< previous page page_385 next page >

Page 385
12180-0385a.gif
Figure 17.2.
The interaction of classes needed to open a file of any type.
12180-0385b.gif
Figure 17.3.
The interaction of classes needed to close a file of any type.
The File Operations Subsystem Class Hierarchy Model
In designing and implementing your own classes for this subsystem, it is important to remember that the classes in it will overlap with the Database Access Subsystem. Both the File Operations Subsystem and the Database Access Subsystem are forms of information persistence mechanisms, and in fact popular databases are nothing more than sophisticated file operation systems.
Figure 17.4 shows the hierarchy of classes related to each file.

 
< previous page page_385 next page >

If you like this book, buy it!